Caller Based Routing Service

Purpose

The Caller Based Routing Service form is used to assign Allow-List and Deny-List service types to callers for using the Caller Based Routing feature. This form is used to configure the Caller Based Routing feature.

Conditions

Field Descriptions

Parameter

Description

Default Value

Caller ID

Enter the caller ID (maximum of 26 digits) of the caller that you want to configure as Allow-List or Deny-List. The caller ID must be unique within the Caller Based Routing Service. This is a mandatory entry.

NOTE: The ID configured for External Hotdesk User ( EHDU) or Direct Inward Dialing (DID) can be configured for Caller Based Routing Service without causing conflicts.

Blank

Primary Node Id (PNI)

Enter the Primary Node Identifier of the destination number (maximum of 7 digits). This is an optional entry.

NOTE: If this field is left blank and the destination number is specified, the system automatically populates the field with the PNI of the cluster where the operation takes place.

Blank

Destination Number

Enter the destination number (maximum of 26 characters) to which the call must be routed. This is a mandatory entry for Allow-List, but is optional for Deny-List.

Blank

Caller Based Routing Service Type

Enter Allow-List or Deny-List service type you want to configure for the Caller ID.

Allow-List